File Names

Overview

ArpaFlow commands that create, copy, or replace files rely on a consistent file naming structure to ensure uniqueness and organization within your projects. The most important aspect is the use of a filename prefix, which helps prevent duplicate names and makes it easy to identify files by project or assembly.

When new components are added to an assembly (using Add or Add Pick), the new file names are generated using the assembly's prefix, followed by a dash, a description, and a numeric index. If the original component already has a prefix or index, these are replaced to match the current assembly's prefix and a new unique index. For copy and replace commands, the prefix is (if present) is inherited from the component being copied or replaced.

All file management commands automatically handle prefix and index assignment, so you only need to ensure your assemblies have a valid prefix before adding components. This system keeps your files organized and avoids naming conflicts.

The prefix may contain spaces and dashes, but the description must not contain a dash. The last dash in the file name is used to separate the prefix from the description. The index is always numeric and located at the end of the file name before the extension.

File Name Format

Prefix - Description-index.

• Index consists of all numeric digits moving backward from the end of the file name (before the extension)
• Description is all text moving backward prior to the index until a dash is located
• Prefix is all text prior to the description and dash

Examples of Valid File Names

The following examples show recommended file naming practices. Including a job number or project code in the prefix is highly recommended for uniqueness.

• 2025-055-OVPR - Main Assembly.iam (prefix contains a job number and item description)
• 2025-055-OVPR - Subcomponent-02.iam (sub component has an index created by an ArpaFlow command)
• OVPR - Subcomponent-01.iam (prefix is a description only without any dashes, and includes an index)
• 2025-055 - Subcomponent-01.iam (prefix is a job number, and includes an index)

The example below is technically valid, but the prefix is not as expected. Because the prefix includes all text up to the last dash, the prefix in this case is: '2025-055-OVPR - Main Assembly'. To correct this, remove the dash from the description.

• 2025-055-OVPR - Main Assembly - more description.iam

Summary

You only need to worry about the file name prefix when you are creating an assembly and plan to use the Add or Add Pick commands to add new components. In these cases, the prefix is required and will be automatically applied to all new components added to the assembly. However, it’s a good idea to always use a prefix for all files in your project, even when it’s not strictly required. Using a prefix helps keep your files organized, makes it easier to avoid duplicate names, and ensures consistency across your assemblies and components.